Call handling based on user profile identification

ABSTRACT

Technologies for handling a call based on user identification include determining a personal profile identification for a user of a communal mobile communication device and initiating a call to a personal communication device using a phone number of the personal communication device and the personal profile identification. The personal communication device may apply a call treatment to the incoming call based on the personal profile identification. Additionally, the personal communication device may originate a call to a call recipient of the communal mobile communication device using a personal profile identification to identify the call recipient. The communal mobile communication device may apply a call treatment to the incoming call based on the personal profile identification.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation application of U.S.application Ser. No. 13/976,034, entitled “CALL HANDLING BASED ON USERPROFILE IDENTIFICATION,” which was filed on Oct. 7, 2013, and which is anational stage entry under 35 U.S.C. §371(b) of InternationalApplication No. PCT/US2011/067384, which was filed on Dec. 27, 2011.

BACKGROUND

Mobile communication devices, such as cellular phones, are becomingubiquitous tools for personal communication and, in the case ofsmartphones, computing. Due to ease of use and accessibility, the use ofmobile communication devices continues to rise. In fact, mobilecommunication devices are becoming so commonplace that some people arereplacing the traditional landline telephones with personal mobilecommunication devices. Doing so, can save the user monthly fees for thelandline telephone, as well as improve accessibility of the user bymaintaining a single phone number at which to reach the user.

In some situations, especially in developing countries, a single mobilecommunication device may be used by more than one user. For example, afamily may replace their traditional landline (or simply not have accessto a traditional landline) with a single “family” mobile communicationdevice. While the use of a “family” mobile communication device providesthe family with the ability to receive and originate communications,difficulties can arise in determining the recipient family member for anincoming call without interrogating the caller. Such difficulties areexacerbated if the mobile communication device is being used for anextended family or community (e.g., a village communication device) inwhich the number of users increases and their familiarity with eachother decreases.

BRIEF DESCRIPTION OF THE DRAWINGS

The concepts described herein are illustrated by way of example and notby way of limitation in the accompanying figures. For simplicity andclarity of illustration, elements illustrated in the figures are notnecessarily drawn to scale. Where considered appropriate, referencelabels have been repeated among the figures to indicate corresponding oranalogous elements.

FIG. 1 is a simplified block diagram of at least one embodiment a systemfor handling incoming and outgoing calls based on personal profileidentification;

FIG. 2 is a simplified block diagram of at least one embodiment of anenvironment of a communal mobile communication device of the system ofFIG. 1;

FIG. 3 is a simplified block diagram of at least one embodiment of anenvironment of a personal mobile communication device of the system ofFIG. 1;

FIG. 4 is a simplified flow diagram of at least one embodiment of amethod for initiating a call using a personal profile identificationthat may be executed by the communal mobile communication device of FIG.2;

FIG. 5 is a simplified flow diagram of at least one embodiment of amethod for receiving a call using a personal profile identification thatmay be executed by the personal mobile communication device of FIG. 3;

FIGS. 6 and 7 are simplified illustrations of user interfaces that maybe displayed on the communal and personal mobile communication devicesduring the execution of the methods of FIGS. 4 and 5;

FIG. 8 is a simplified flow diagram of at least one embodiment of amethod for initiating a call using a personal profile identificationthat may be executed by the personal mobile communication device of FIG.3;

FIG. 9 is a simplified flow diagram of at least one embodiment of amethod for receiving a call using a personal profile identification thatmay be executed by the communal mobile communication device of FIG. 2;and

FIGS. 10 and 11 are simplified illustrations of user interfaces that maybe displayed on the communal and personal mobile communication devicesduring the execution of the methods of FIGS. 8 and 9.

DETAILED DESCRIPTION OF THE DRAWINGS

While the concepts of the present disclosure are susceptible to variousmodifications and alternative forms, specific embodiments thereof havebeen shown by way of example in the drawings and will be describedherein in detail. It should be understood, however, that there is nointent to limit the concepts of the present disclosure to the particularforms disclosed, but on the contrary, the intention is to cover allmodifications, equivalents, and alternatives consistent with the presentdisclosure and the appended claims.

References in the specification to “one embodiment,” “an embodiment,”“an illustrative embodiment,” etc., indicate that the embodimentdescribed may include a particular feature, structure, orcharacteristic, but every embodiment may or may not necessarily includethat particular feature, structure, or characteristic. Moreover, suchphrases are not necessarily referring to the same embodiment. Further,when a particular feature, structure, or characteristic is described inconnection with an embodiment, it is submitted that it is within theknowledge of one skilled in the art to effect such feature, structure,or characteristic in connection with other embodiments whether or notexplicitly described.

The disclosed embodiments may be implemented, in some cases, inhardware, firmware, software, or any combination thereof. The disclosedembodiments may also be implemented as instructions carried by or storedon a transitory or non-transitory machine-readable (e.g.,computer-readable) storage medium, which may be read and executed by oneor more processors. A machine-readable storage medium may be embodied asany storage device, mechanism, or other physical structure for storingor transmitting information in a form readable by a machine (e.g., avolatile or non-volatile memory, a media disc, or other media device).

In the drawings, some structural or method features may be shown inspecific arrangements and/or orderings. However, it should beappreciated that such specific arrangements and/or orderings may not berequired. Rather, in some embodiments, such features may be arranged ina different manner and/or order than shown in the illustrative figures.Additionally, the inclusion of a structural or method feature in aparticular figure is not meant to imply that such feature is required inall embodiments and, in some embodiments, may not be included or may becombined with other features.

Referring now to FIG. 1, in the illustrative embodiment, a system 100for handling incoming and outgoing calls based on user profileidentification includes a communal mobile communication device 102, apersonal mobile communication device 104, and a communication network106 over which the devices 102, 104 may communicate. The communal mobilecommunication device 102 is illustratively embodied as a mobilecommunication device designated for use by multiple users. For example,the communal mobile communication device 102 may be embodied as a familyphone used by the members of the family, as a village phone used byvarious members of a village in a developing country, or as any othertype of public or semi-public phone used by members of a particulargroup (e.g., a business unit, a club, etc.). Alternatively, in someembodiments, the communal mobile communication device 102 may be usedprimarily by a single person but for different purposes such as for bothpersonal and business uses. Conversely, the personal mobilecommunication device 104 is illustratively embodied as a personal phoneused by a single person or primarily by a single person. However, insome embodiments, the personal mobile communication device 104 may beembodied as a communal phone similar to the communal mobilecommunication device 102, as a public phone, or as a typical phone orcommunication device.

In use, as discussed in more detail below, the communal mobilecommunication device 102 facilitates multiple users by allowing eachuser to select a personal profile identification, which uniquelyidentifies each user from the other users of the communal mobilecommunication device 102. The personal profile identification allows thecall recipient of the personal mobile communication device 104 toidentify not only that the call originated from the communal mobilecommunication device 102 as typical but also the identity of the personusing the communal mobile communication device 102 to originate thecall. That is, the communal mobile communication device 102 mayoriginate calls to the personal mobile communication device 104 (orother communication device) using the personal profile identification.For example, the generated call may use the recipient phone number ofthe personal mobile communication device 104, the phone number of thecommunal mobile communication device 102, and the user's call profileidentification. Typically, when receiving a call on the personal mobilecommunication device 104 from a standard communication device, the userof the personal mobile communication device 104 is only able to identifythe calling number (i.e., usually the owner or primary user of thecalling number). However, because the incoming call includes thepersonal profile identification, the personal mobile communicationdevice 104 may identify the particular user of the communal mobilecommunication device 102 and apply call treatments personalized to thatuser (e.g., a customized ringtone for each different user of thecommunal mobile communication device).

The use of the personal profile identification to identify the varioususers of the communal mobile communication device 102 also allows theuser of the personal mobile communication device 104 to call aparticular user of the communal mobile communication device 102. To doso, the personal mobile communication device 104 originates the callusing the call recipient's personal profile identification, which may belocally stored. Upon receiving the call, the communal mobilecommunication device 102 determines the call recipient based on thepersonal profile identification included in the incoming call andannounces the call using a call treatment, which may be customized forthe call recipient (e.g., a picture of call recipient may be displayedon the communal mobile communication device 102).

The communal mobile communication device 102 may be embodied as any typeof mobile communication device capable of performing the functionsdescribed herein. For example, in some embodiments, the communal mobilecommunication device 102 may be embodied as a “smart” phone, a cellphone, a tablet computer, a laptop computer, a mobile appliance device,or other mobile computing device capable of communications over thenetwork 106. As shown in FIG. 1, the illustrative communal mobilecommunication device 102 includes a processor 110, a memory 112, aninput/output subsystem 114, a display 116, a communication circuit 118,and a data storage 120. Of course, the communal mobile communicationdevice 102 may include other or additional components, such as thosecommonly found in a mobile communication device and/or computing devices(e.g., various input/output devices), in other embodiments.Additionally, in some embodiments, one or more of the illustrativecomponents may be incorporated in, or otherwise from a portion of,another component. For example, the memory 112, or portions thereof, maybe incorporated in the processor 110 in some embodiments.

The processor 110 may be embodied as any type of processor capable ofperforming the functions described herein. For example, the processormay be embodied as a single or multi-core processor(s) having one ormore processor cores, a digital signal processor, a microcontroller, orother processor or processing/controlling circuit. Similarly, the memory112 may be embodied as any type of volatile or non-volatile memory ordata storage currently known or developed in the future and capable ofperforming the functions described herein. In operation, the memory 112may store various data and software used during operation of thecommunal mobile communication device 102 such as operating systems,applications, programs, libraries, and drivers.

The memory 112 is communicatively coupled to the processor 110 via theI/O subsystem 113, which may be embodied as circuitry and/or componentsto facilitate input/output operations with the processor 110, the memory112, and other components of the communal mobile communication device102. For example, the I/O subsystem 114 may be embodied as, or otherwiseinclude, memory controller hubs, input/output control hubs, firmwaredevices, communication links (i.e., point-to-point links, bus links,wires, cables, light guides, printed circuit board traces, etc.) and/orother components and subsystems to facilitate the input/outputoperations. In some embodiments, the I/O subsystem 114 may form aportion of a system-on-a-chip (SoC) and be incorporated, along with theprocessor 110, the memory 112, and other components of the communalmobile communication device 102, on a single integrated circuit chip.

The display 116 of the communal mobile communication device 102 may beembodied as any type of display on which information may be displayed toa user of the communal mobile communication device 102. In someembodiments, for example, the display 116 may be embodied as atouchscreen display and includes a corresponding touchscreen sensor (notshown) to receive tactile input (e.g., a tactile input gesture) and dataentry from the user. The display 116 may be embodied as, or otherwiseuse, any suitable display technology including, for example, a liquidcrystal display (LCD), a light emitting diode (LED) display, a cathoderay tube (CRT) display, a plasma display, and/or other display usable ina mobile computing device.

The communication circuit 118 may be embodied as one or more devicesand/or circuitry for enabling communications between the communal mobilecommunication device 102 and the personal mobile communication device104. The communication circuit 118 may be configured to use any suitablecommunication protocol to communicate with the personal mobilecommunication device 104 over the network 106 including, for example,cellular communication protocols, wireless data communication protocols,and/or wired data communication protocols.

The data storage 120 may be embodied as any type of device or devicesconfigured for the short-term or long-term storage of data such as, forexample, memory devices and circuits, memory cards, hard disk drives,solid-state drives, or other data storage devices. In the illustrativeembodiment, the data storage 120 may store a personal profile database122 and an incoming call policy database 124. The personal profiledatabase 122 stores the personal profile identifications for each of theauthorized or “registered” users of the communal mobile communicationdevice 102. Each personal profile identification uniquely identifies theassociated user from other users of the communal mobile communicationdevice 102 and may be embodied as any type of identifier including, butnot limited to, a numerical sequence, an alphanumerical passkey, apassword, an e-mail address, and/or other identification data capable ofuniquely identifying the associated user. In some embodiments asdiscussed below, access to each personal profile identification isprotected (e.g., via password protection) such that only the associateduser can access his/her personal profile identification.

The incoming call policy database 124 stores call treatment dataidentifying particular call treatments to be applied to an incomingcall. The call treatment data is associated with individual personalprofile identifications such that an incoming call for a particular userof the communal mobile communication device 102 may receive a customizedcall treatment (e.g., a customized ringtone) such that the users of thecommunal mobile communication device 102 are alerted to the intendedrecipient of the call. In some embodiments, the call treatment data mayalso be associated with the phone number of the communication deviceoriginating the incoming call such that the communal mobilecommunication device 102 may announce the call based on caller, as wellas the intended call recipient. Additionally, in some embodiments, theincoming call policy database 124 is embodied in, or otherwise forms aportion of, the personal profile database 122. That is, the personalprofile database 122 and/or the incoming call policy database 124 may beincorporated into a common database. For example, in the illustrativeexample, each of the personal profile database 122 and/or the incomingcall policy database 124 is embodied in, or otherwise included in, acontacts database 208 (see FIG. 2) of the communal mobile communicationdevice 102.

In some embodiments, the communal mobile communication device 102 mayfurther include one or more peripheral devices 126. Such peripheraldevices 126 may include any type of peripheral device commonly found ina mobile communication device or computing device as other data storagedevices, speakers, a hardware keyboard, input/output devices, peripheralcommunication devices, and/or other peripheral devices.

Similar to the communal mobile communication device 102, the personalmobile communication device 104 may be embodied as any type of mobilecommunication device capable of performing the functions describedherein. For example, in some embodiments, the personal mobilecommunication device 104 may be embodied as a “smart” phone, a cellphone, a tablet computer, a laptop computer, a mobile appliance device,or other mobile computing device capable of communications over thenetwork 106. As shown in FIG. 1, the illustrative personal mobilecommunication device 104 includes a processor 130, a memory 132, aninput/output subsystem 134, a display 136, a communication circuit 138,and a data storage 140. Of course, the personal mobile communicationdevice 104 may include other or additional components, such as thosecommonly found in a mobile communication device and/or computing devices(e.g., various input/output devices), in other embodiments.

The components of the personal mobile communication device 104 may besimilar to the corresponding components of the communal mobilecommunication device 102. As such, the description of those componentsof the communal mobile communication device 102 is equally applicable tothe corresponding components of the personal mobile communication device104 and is not repeated herein for clarify of the description. Forexample, the data storage 140 of the personal mobile communicationdevice 104 may be similar to the data storage 120 of the communal mobilecommunication device 102 and may be embodied as any type of device ordevices configured for the short-term or long-term storage of data suchas, for example, memory devices and circuits, memory cards, hard diskdrives, solid-state drives, or other data storage devices. In theillustrative embodiment, the data storage 140 may store an incoming callpolicy database 142 and a personal profile database 144. Similar to theincoming call policy 124 of the communal mobile communication device102, the incoming call policy 142 of the personal mobile communicationdevice 104 stores call treatment data identifying particular calltreatments to be applied to an incoming call based on the personalprofile identification included in the incoming call. That is, the calltreatment data is associated with individual personal profileidentifications such that the personal mobile communication device 104may announce the particular user of the communal mobile communicationdevice 102 as the caller. For example, the personal mobile communicationdevice 104 may have a ringtone assigned to one particular user (e.g., ason) of the communal mobile communication device 102 and a differentringtone assigned to a different particular user (e.g., a daughter). Inthis way, the user of the personal mobile communication device 104 ismade aware of the identity of the caller even though the same communalmobile communication device 102 is used by both users.

The personal profile database 144 of the personal mobile communicationdevice 104 is similar to the personal profile database 122 of thecommunal mobile communication device 102 and stores the personal profileidentifications for various users of the communal mobile communicationdevice 102. When originating a call to a particular user of the communalmobile communication device 102, the personal mobile communicationdevice 104 may retrieve the personal profile identification of the callrecipient. The personal mobile communication device 104 originates thecall using the personal profile identification to allow the communalmobile communication device 102 to announce the incoming call for theparticular user as discussed above. In some embodiments, the incomingcall policy 142 and/or the personal profile database 144 may beincorporated in to a common database. For example, in the illustrativeexample, each of the incoming call policy database 142 and the personalprofile database 144 is embodied in, or otherwise included in, acontacts database 308 (see FIG. 3) of the personal mobile communicationdevice 104.

Referring now to FIG. 2, in the illustrative embodiment, the communalmobile communication device 102 establishes an environment 200 duringoperation. The illustrative environment 200 includes an outgoing callhandler module 202, a communication module 204, an incoming call handlermodule 206, the personal profile database 122, and the incoming callpolicy database 124. The various modules of the environment 200 may eachbe embodied as software, firmware, hardware, or a combination thereof.The outgoing call handler module 202 manages the outgoing callsoriginating from the communal mobile communication device 102 via thecommunication module 204. For example, the outgoing call handler module202 may present a user interface (e.g., a graphical user interface) onthe display 116. A user of the communal mobile communication device 102may select the desired user account (i.e., select the identity of thecaller) from the user interface (or may simply enter a passcode toautomatically select the desired user account). As discussed above, theselection of a particular caller identity on the communal mobilecommunication device 102 may be protected via a password, passkey, orother security measure. If the user is properly authenticated, theoutgoing call handler module 202 retrieves the personal profileidentification associated with the selected user from the personalprofile database 122. The communal mobile communication device 102subsequently originates the outgoing call to the personal mobilecommunication device 104 (or other desired recipient communicationdevice) using the personal profile identification. Because the outgoingcall includes the personal profile identification, the personal mobilecommunication device 104 (or other recipient communication device) isable to announce the particular caller to the user of the personalmobile communication device 104.

The incoming call handler module 206 manages the handling of incomingcalls to the communal mobile communication device 102 received via thecommunication module 204. For example, the incoming call handler module206 monitors for incoming calls that include a personal profileidentification. If the incoming call includes a personal profileidentification, the incoming call handler module 206 retrieves calltreatment data from the incoming call policy database 124 based on thepersonal profile identification. The incoming call handler module 206subsequently announces the incoming call using the retrieved calltreatment data (e.g., by playing particular ringtone or displaying aparticular image on the display 116).

Referring now to FIG. 3, in the illustrative embodiment, the personalmobile communication device 104 establishes an environment 300 duringoperation. The illustrative environment 300 includes an incoming callhandler module 302, a communication module 304, an outgoing call handlermodule 306, the incoming call policy database 142, and the personalprofile database 122, and the incoming call policy database 124. Thevarious modules of the environment 300 may each be embodied as software,firmware, hardware, or a combination thereof. The incoming call handlermodule 302 handles incoming calls received on the personal mobilecommunication device 104 via the communication module 304. For example,similar to the incoming call handler module 206, the incoming callhandler module 302 determines whether the incoming call includes apersonal profile identification. If so, the incoming call handler module304 retrieves call treatment data from the incoming call policy database142 based on the personal profile identification and subsequentlyannounces the incoming call to the user of the personal mobilecommunication device 104 using the call treatment data (e.g., by playinga particular ringtone or displaying a particular image on the display136).

The outgoing call handler module 306 manages the origination of callsfrom the personal mobile communication device 104. In embodiments inwhich the user of the personal mobile communication device 104 desiresto call a particular user of the communal mobile communication device102, the outgoing call handler module 306 may retrieve the personalprofile identification associated with the desired call recipient fromthe personal profile database 144. In some embodiments, the personalprofile database 144 is incorporated in, or otherwise associated with, acontacts database 308 of the personal mobile communication device 104.In such embodiments, the user of the personal mobile communicationdevice 104 may simply select the call recipient from the contactsdatabase 308. In response, the outgoing call handler module 306retrieves the associated personal profile identification. Regardless,the outgoing call handler module 306 originates the call to the communalmobile communication device 102 using the retrieved personal profileidentification. Because the outgoing call includes the personal profileidentification of the desired call recipient, the communal mobilecommunication device 102 is able to announce the particular callrecipient (e.g., by playing a particular ringtone).

Referring now to FIG. 4, in use, the communal mobile communicationdevice 102 may execute a method 400 for initiating a call using apersonal profile identification. The method 400 begins with block 402 inwhich the communal mobile communication device 102 determines whetherthe user desires to initiate a call. For example, the user may select a“call” button from a graphical user interface displayed on the display116 of the communal mobile communication device 102 or the user maysimply enter the call recipient's telephone number in block 402. If thecommunal mobile communication device 102 determines the user desires tomake a call, the method 400 advances to block 404 in which the user mayselect the caller identity. For example, in some embodiments, thecommunal mobile communication device 102 may present a selection menu ofauthorized users by name, picture, or other identification. The user mayselect the caller identity to be used. As discussed above, in someembodiments, the communal mobile communication device 102 mayauthenticate that the user is authorized to use the selected calleridentity in block 406. For example, in response to a user selecting oneof the caller identities from a list displayed on the display 116, thecommunal mobile communication device 102 may prompt the user for anassociated password, passkey, or other verification mechanism. In thisway, the use of personal profile identifications may be protected.

If the user is successfully authenticated in block 406 (or if noauthentication is used), the method 400 advances to block 408 in whichthe communal mobile communication device 102 determines whether apersonal profile identification for the selected user is available inthe personal profile database 122. That is, the communal mobilecommunication device 102 determines whether the user has previouslyset-up or registered a personal profile identification. If so, thecommunal mobile communication device 102 retrieves the personal profileidentification associated with the selected call identity (i.e.,associated with the user) in block 410. However, if no personal profileidentification is available, the communal mobile communication device102 assigns a default personal profile identification in block 412. Thedefault personal profile identification may be embodied as any type ofidentification and may, in some embodiments, identity only that the callis originating from the communal mobile communication device 102.Alternatively, in some embodiments, the default personal profileidentification may be embodied as a null set (i.e., no personal profileidentification is assigned). In some embodiments, the user of thecommunal mobile communication device 102 may enter a personal profileidentification at the time of the call if, for example, the personalprofile identification is not stored on the communal mobilecommunication device 102.

In block 414, the communal mobile communication device 102 originatesthe outgoing call using the phone number of the recipient communicationdevice (e.g. the personal mobile communication device 104) and thepersonal profile identification retrieved in block 410. The phone numberof the recipient communication device may be entered directly by theuser of the communal mobile communication device 102 or may be suppliedby selection of the call recipient from the contacts database 208 of thecommunal mobile communication device 102. Regardless, in block 416, thephone number of the communal mobile communication device 102 is appendedto the phone number of the recipient communication device (e.g., thepersonal mobile communication device 104) and the personal profileidentification is append to the phone numbers of the recipientcommunication device and the communal mobile communication device 102 inblock 418. As discussed above, the personal profile identification maybe embodied as any type of identifier that uniquely identified theassociated user from other users of the communal mobile communicationdevice including, for example, a numerical sequence, an alphanumericalpasskey, a password, an e-mail address, and/or other identification datacapable of uniquely identifying the associated user. The particularmechanism used to append the personal profile identification to theoutgoing phone numbers may depend on the implementation and type ofnetwork 106. For example, in some embodiments, the mobile switchingcenters 150 of the network 106 may be modified to handle calls havinglonger origination and/or destination numbers to support the use of thepersonal profile identifications.

In some embodiments, in block 420, the communal mobile communicationdevice 102 may record one or more call metrics of the current call. Suchcall metrics may be embodied as any type of metric related to thecurrent call such as minute usage, call history, call logs, and soforth. In some embodiments, the communal mobile communication device 102records the metrics for each individual user. By recording the callmetrics on a per-user basis, the individual users may monitor theirusage of the communal mobile communication device 102. Additionally,each user may be separately billed for their individual usage, eventhough the communal mobile communication device 102 is used by multipleusers.

Subsequently, in block 424, the communal mobile communication device 102determines whether the call is completed. If not, the method 400 loopsback to block 420 to continue recording call metrics (in someembodiments). However, if the call is completed, the call is ended inblock 426, and the method 400 loops back to block 402 to await theinitiating of a new call.

Referring now to FIG. 5, in use, the personal mobile communicationdevice 104 may execute a method 500 for receiving a call using apersonal profile identification. The method 500 begins with block 502 inwhich the personal mobile communication device 104 determines whether anincoming call has been received. If so, in block 504, the personalmobile communication device 104 determines whether the caller's phonenumber, which is received with the incoming call, is in the contactsdatabase 308 of the personal mobile communication device 104. If not,the method 500 advances to block 506 in which the personal mobilecommunication device 104 announces the incoming call as an unknowncaller (e.g., using a default ringtone and displaying “unknown caller”on the display 136).

If, however, the caller's phone number is in the contacts database 308,the method 500 advances to block 508 in which the personal mobilecommunication device 104 determines whether the incoming call includes apersonal profile identification. If not, the personal mobilecommunication device 104 sets a default call treatment for the incomingcall in block 510 (or sets the call treatment based only on the caller'sphone number). If, however, the incoming call does include a personalprofile identification, the personal mobile communication device 104determines whether the personal profile identification is in thepersonal profile database 144, which may be included in the contactsdatabase 308 as discussed above. If not, the method advances to block510 in which the personal mobile communication device 104 sets a defaultcall treatment for the incoming call.

If, however, the personal profile identification included in theincoming call is included in the personal profile database 144, themethod 500 advances to block 514 in which the personal mobilecommunication device 104 determines whether a call treatment has beenset for the particular personal profile identification. To do so, thepersonal mobile communication device 104 may compare the personalprofile identification to the incoming call policy database 142 todetermine whether a call treatment has been set for the particularpersonal profile identification. If not, the personal mobilecommunication device 104 sets a default call treatment for the incomingcall in block 510. If, however, a call treatment has been set for theparticular personal profile identification, the method 500 advances toblock 516 in which the personal mobile communication device 104retrieves call treatment data for the incoming call based on thepersonal profile identification from the incoming call policy database142. The call treatment data may be embodied as any type of data thatdefines how the incoming call should be announced or otherwise handled.For example, the call treatment data may include a ringtone that is tobe played, a picture or image that is to be displayed, and/or otheractions that should be performed to announce, or otherwise handle, theincoming call.

In block 518, the personal mobile communication device 104 announces thecall to the user of the personal mobile communication device 104 usingthe call treatment (if any) previously determined for the call. Forexample, the personal mobile communication device 104 may display apicture of the caller based on the personal profile identificationincluded in the incoming call in block 520. Additionally oralternatively, the personal mobile communication device 104 may play aparticular ringtone associated with the caller based on the personalprofile identification included in the incoming call in block 522. Ofcourse, the personal mobile communication device 104 may use othermechanisms and/or data to announce the call in other embodimentsincluding different types of vibrations, display of the caller's phonenumber, and so forth.

Referring now to FIGS. 6 and 7, illustrative user interfaces displayedon the displays 116, 136 to users of the communal and personal mobilecommunication devices 102, 104 during execution of the methods 400 and500 are shown. For example, in the illustrative embodiment of FIG. 6, auser of the communal mobile communication device 102 has selected acaller identity “Mary Jane” from a list 602 of caller identitiespresented on a user interface 600 of the communal mobile communicationdevice 102 and originated a call 610 to a call recipient 604 (“Dad”) ofthe personal mobile communication device 104. As shown, the call 610includes the personal profile identification associated with the user“Mary Jane.” As such, in response to receiving the call, the personalmobile communication device 104 announces the call using a calltreatment based on the received personal profile identification. Forexample, in the illustrative embodiment, the personal mobilecommunication device 104 may display an image 622 of the caller “MaryJane” on a user interface 620 displayed on the display 136.Additionally, the personal mobile communication device 104 announces thecall using a ringtone 624 (“Rock”) customized for the particularpersonal profile identification (i.e., for the particular caller “MaryJane”).

Similarly, in the illustrative embodiment of FIG. 7, a different user ofthe communal mobile communication device 102 has selected a calleridentity “Sam” from the list 602 of caller identities presented on theuser interface 600 of the communal mobile communication device 102 andoriginated a call 710 to a call recipient 604 (“Dad”) of the personalmobile communication device 104. As shown, the call 710 includes thepersonal profile identification associated with the user “Sam.” As such,in response to receiving the call, the personal mobile communicationdevice 104 announces the call using a call treatment based on thereceived personal profile identification. For example, in theillustrative embodiment, the personal mobile communication device 104may display an image 722 of the caller “Sam” on the user interface 620and announces the call using a ringtone 724 (“Dubstep”) customized forthe particular personal profile identification (i.e., for the particularcaller “Sam”). In this way, the user of the personal mobilecommunication device 104 is informed of the particular caller using thecommunal mobile communication device 102.

Referring now to FIG. 8, in some embodiments, the personal mobilecommunication device 104 may also originate calls using the personalprofile identification of the intended call recipient. That is, a userof the personal mobile communication device 104 may originate a call toone of the users of the communal mobile communication device 102 usingthe personal profile identification associated with the intended callrecipient such that the communal mobile communication device 102 mayannounce the call for the particular call recipient (i.e., theparticular user of the communal mobile communication device 102). To doso, the personal mobile communication device 104 may execute a method800 for initiating a call using personal profile identification. Themethod 800 begins with block 802 in which the personal mobilecommunication device 104 determines whether the user desires to initiatea call. If so, the method 800 advances to block 804 in which the userselects the desired call recipient. For example, in some embodiments,the user may select the desired call recipient from the contactsdatabase 308 or otherwise supply the identification data of the desiredcall recipient (e.g., the user may supply a partial name to cause thepersonal mobile communication device 104 to retrieve the intended callrecipient from the contacts database 308). Subsequently, in block 806,the personal mobile communication device 104 retrieves the phone numberassociated with the selected call recipient (e.g., the phone number ofthe communal mobile communication device 102). In block 808, thepersonal mobile communication device 104 determines whether a personalprofile identification for the selected call recipient is available inthe personal profile database 144. If not, the personal mobilecommunication device 104 initiates the call as normal in block 810.

If, however, a personal profile identification is available of theintended call recipient, the personal mobile communication device 104retrieves the personal profile identification from the personal profiledatabase 144 in block 812. In block 814, the personal mobilecommunication device 104 initiates the call using the call recipient'sphone number and the personal profile identification retrieved in block812. For example, in block 816, the phone number of the personal mobilecommunication device 104 may be appended to the phone number of therecipient communication device (e.g., the communal mobile communicationdevice 102) and the personal profile identification is append to thephone numbers of the recipient communication device and the personalmobile communication device 104 in block 818. As discussed above, theparticular mechanism used to append the personal profile identificationto the outgoing phone numbers may depend on the implementation and typeof network 106.

Subsequently, in block 820, the personal mobile communication device 104determines whether the call is completed. If not, the method 800 loopsback to block 820 to continue checking for the completion of the call.However, if the call is completed, the call is ended in block 822, andthe method 800 loops back to block 802 to await the initiating of a newcall.

Referring now to FIG. 9, in some embodiments, the communal mobilecommunication device 102 may also execute a method 900 for handlingincoming calls using personal profile identifications. The method 900begins with block 902 in which the communal mobile communication device102 determines whether an incoming call has been received. If so, inblock 904, the communal mobile communication device 102 determineswhether the caller's phone number, which is received with the incomingcall, is in the contacts database 208 of the communal mobilecommunication device 102. If not, the method 900 advances to block 906in which the communal mobile communication device 102 announces theincoming call as an unknown caller (e.g., using a default ringtone anddisplaying “unknown caller” on the display 136).

If, however, caller's phone number is in the contacts database 208, themethod 900 advances to block 908 in which the communal mobilecommunication device 102 determines whether the incoming call includes apersonal profile identification. If not, the communal mobilecommunication device 102 sets a default call treatment for the incomingcall in block 910 (or sets the call treatment based only on the caller'sphone number). If, however, the incoming call does include a personalprofile identification, the communal mobile communication device 102determines whether the personal profile identification is in thepersonal profile database 122, which may be included in the contactsdatabase 208 as discussed above, in block 912. If not, the method 900advances to block 910 in which the communal mobile communication device102 sets a default call treatment for the incoming call.

If, however, the personal profile identification included in theincoming call is included in the personal profile database 122, themethod 900 advances to block 914 in which the communal mobilecommunication device 102 determines whether a call treatment has beenset for the particular personal profile identification. To do so, thecommunal mobile communication device 102 may compare the personalprofile identification to the incoming call policy database 124 todetermine whether a call treatment has been set for the particularpersonal profile identification. If not, the communal mobilecommunication device 102 sets a default call treatment for the incomingcall in block 910. If, however, a call treatment has been set for theparticular personal profile identification, the method 900 advances toblock 916 in which the communal mobile communication device 102retrieves call treatment data for the incoming call based on thepersonal profile identification from the incoming call policy database124.

In block 518, the communal mobile communication device 102 announces thecall using the call treatment (if any) previously determined for theincoming call. For example, the communal mobile communication device 102may display a picture of the call recipient based on the personalprofile identification included in the incoming call in block 920.Additionally or alternatively, the communal mobile communication device102 may play a particular ringtone associated with the call recipientbased on the personal profile identification included in the incomingcall in block 522. Additionally, in some embodiments, the communalmobile communication device 102 may display a picture or otheridentification associated with the caller in block 924. Of course, thecommunal mobile communication device 102 may use other mechanisms and/ordata to announce the call in other embodiments including different typesof vibrations, display of the caller's phone number, and so forth.

Referring now to FIGS. 10 and 11, illustrative user interfaces displayedon the displays 116, 136 to users of the communal and personal mobilecommunication devices 102, 104 during execution of the methods 800 and900 are shown. For example, in the illustrative embodiment of FIG. 10, auser of the personal mobile communication device 104 has selected acaller recipient “Mom” from a contact list 1002 of available callrecipients presented on a user interface 1000 of the personal mobilecommunication device 104 and originated a call 1010 to the callrecipient 1004 (“Mom”) of the communal mobile communication device 102.As shown, the call 1010 includes the personal profile identificationassociated with the user “Mom” of the communal mobile communicationdevice 102. As such, in response to receiving the call, the communalmobile communication device 102 announces the call using a calltreatment based on the received personal profile identification. Forexample, in the illustrative embodiment, the communal mobilecommunication device 102 may indicate the call recipient in a displaybox 1022 on a user interface 1020 and announce the call using a ringtone1024 (“Jazz”) customized for the particular personal profileidentification (i.e., for the particular call recipient “Mom”).Additionally, the communal mobile communication device 102 may displayan image 1026 of the caller “Dad” on the user interface 1020.

Similarly, in the illustrative embodiment of FIG. 11, the user of theuser of the personal mobile communication device 104 has selected adifferent user of the communal mobile communication device 102 as thecall recipient. In the illustrative embodiment, the user of the personalmobile communication device 104 has selected a caller recipient “Sam”from the contact list 1002 and originated a call 1110 to the callrecipient 1104 (“Sam”) of the communal mobile communication device 102.As shown, the call 1110 includes the personal profile identificationassociated with the user “Sam” of the communal mobile communicationdevice 102. As such, in response to receiving the call, the communalmobile communication device 102 announces the call using a calltreatment based on the received personal profile identification. Forexample, in the illustrative embodiment, the communal mobilecommunication device 102 may indicate the call recipient in the displaybox 1022 and announce the call using a ringtone 1124 (“Dubstep”)customized for the particular personal profile identification (i.e., forthe particular call recipient “Sam”).

EXAMPLES

Illustrative examples of the technologies disclosed herein are providedbelow. An embodiment of the technologies may include any one or more,and any combination of, the examples described below.

Example 1 includes a communal mobile communication device for handlingcalls based on user identification, the communal mobile communicationdevice comprising an outgoing call handler module to (i) determine apersonal profile identification that identifies a user of the communalmobile communication device from other users, (i) determine a phonenumber of a personal mobile communication device of a call recipientselected to receive a call from the communal mobile communicationdevice, and (iii) initiate the call to the personal mobile communicationdevice using the phone number and the personal profile identification toidentify the user.

Example 2 includes the subject matter of Example 1, and wherein thecommunal mobile communication device further comprises a display; and apersonal profile database having stored therein personal profileidentifications for users of the communal mobile communication device,wherein to determine the personal profile identification comprises topresent a menu of authorized users of the communal mobile communicationdevice on the display; receive a selection of one of the authorizedusers from the user; and retrieve a personal profile identification ofthe selected authorized user from the personal profile database.

Example 3 includes the subject matter of any of Examples 1 and 2, andwherein the communal mobile communication device further comprises apersonal profile database having stored therein personal profileidentifications for users of the communal mobile communication device,and wherein retrieving the personal profile identification comprises toauthenticate the user to access the personal profile identification; andretrieve the personal profile identification from the personal profiledatabase in response to authenticating the user.

Example 4 includes the subject matter of any of Examples 1-3, andfurther including a display, and wherein to authenticate the usercomprises to receive a passkey from the user via a user interfacedisplayed on the display, and authenticate the user based on thereceived passkey.

Example 5 includes the subject matter of any of Examples 1-4, andwherein the communal mobile communication device further comprises apersonal profile database having stored therein personal profileidentifications for users of the communal mobile communication device,and wherein to determine the personal profile identification comprisesto authenticate the user to the communal mobile communication device;and retrieve, in response to authentication of the user, a personalprofile identification from the personal profile database based on theauthentication of the user.

Example 6 includes the subject matter of any of Examples 1-5, andwherein to authenticate the user comprises to determine whether apersonal profile identification for the authenticated user exists in thepersonal profile database; and set the personal profile identificationto a default personal profile identification in response to thedetermination that the personal profile identification for the user doesnot exist in the personal profile database.

Example 7 includes the subject matter of any of Examples 1-6, andwherein the personal profile identification comprises a numericalsequence that uniquely identifies the user from other authorized usersof the communal mobile communication device.

Example 8 includes the subject matter of any of Examples 1-7, andwherein the personal profile identification comprises an e-mail addressthat uniquely identifies the user from other authorized users of thecommunal mobile communication device.

Example 9 includes the subject matter of any of Examples 1-8, andwherein the personal profile identification comprises a passkey thatuniquely identifies the user from other authorized users of the communalmobile communication device.

Example 10 includes the subject matter of any of Examples 1-9, andfurther including a contacts database having stored therein phonenumbers of contacts of the user, and wherein to determine the phonenumber of the personal mobile communication device comprises to retrievethe phone number from the contacts database.

Example 11 includes the subject matter of any of Examples 1-10, andfurther including a display, and wherein to determine the phone numberof the personal mobile communication device comprises to receive thephone number from the user via a user interface displayed on thedisplay.

Example 12 includes the subject matter of any of Examples 1-11, andwherein to initiate the call comprises to append the phone number of thecommunal mobile communication device to the phone number of the personalmobile communication device.

Example 13 includes the subject matter of any of Examples 1-12, andwherein to initiate the call comprises to append the personal profileidentification to the phone number of the communal mobile communicationdevice and the phone number of the personal mobile communication device.

Example 14 includes the subject matter of any of Examples 1-13, andwherein to initiate the call comprises to generate an outgoing phonenumber comprising (i) the phone number of the personal mobilecommunication device, (ii) the phone number of the communal mobilecommunication device, and (iii) the personal profile identification.

Example 15 includes the subject matter of any of Examples 1-14, andwherein the outgoing call handler further to record call metrics of thecall for the user of the communal mobile communication device.

Example 16 includes the subject matter of any of Examples 1-15, andfurther including an incoming call handler module to receive an incomingcall including a personal profile identification identifying a callrecipient to receive the call; determine a call treatment for theincoming call based on the personal profile identification; and announcethe incoming call on the communal mobile communication device using thedetermined call treatment.

Example 17 includes the subject matter of any of Examples 1-16, andfurther including a personal profile database having stored thereinpersonal profile identifications for user of the communal mobilecommunication device, and wherein to determine the call treatment forthe incoming call comprises to retrieve call treatment data from thepersonal profile database based on the personal profile identification.

Example 18 includes the subject matter of any of Examples 1-17, andfurther including a personal profile database having stored thereinpersonal profile identifications for user of the communal mobilecommunication device, and wherein to determine the call treatmentcomprises to apply a default call treatment in response to the personalprofile identification for the user not existing in the personal profiledatabase.

Example 19 includes the subject matter of any of Examples 1-18, andfurther including a display, wherein to determine the call treatmentcomprises to retrieve an image associated with the call recipient basedon the personal profile identification, and wherein to announce theincoming call comprises to display the image on the display.

Example 20 includes the subject matter of any of Examples 1-19, andwherein to determine the call treatment comprises to retrieve a ringtoneassociated with the call recipient based on the personal profileidentification, and to announce the incoming call comprises to play theringtone on the communal mobile communication device.

Example 21 includes the subject matter of any of Examples 1-20, andwherein to announce the incoming call comprises to displayidentification data of a caller based on a phone number of a personalcommunication device that originated the incoming call.

Example 22 includes a method for handling a call based on useridentification, the method comprising determining a personal profileidentification for a user of a communal mobile communication device, thepersonal profile identification identifying the user from other users ofthe communal mobile communication device; determining, on the communalmobile communication device, a phone number of a personal mobilecommunication device of a call recipient selected to receive the call;and initiating the call from the communal mobile communication device tothe personal mobile communication device using the phone number and thepersonal profile identification to identify the user.

Example 23 includes the subject matter of Example 22, and whereindetermining the personal profile identification comprises presenting amenu of authorized users of the communal mobile communication device ona display of the communal mobile communication device; receiving aselection of one of the authorized users; and retrieving a personalprofile identification of the selected authorized user from a personalprofile database.

Example 24 includes the subject matter of any of Examples 22 and 23, andwherein retrieving a personal profile identification comprisingauthenticating the user to access the personal profile identification;and retrieving the personal profile identification from a personalprofile database of the communal mobile communication device in responseto authenticating the user.

Example 25 includes the subject matter of any of Examples 22-24, andwherein authenticating the user comprises receiving a passkey from theuser via a user interface of the communal mobile communication deviceand authenticating the user based on the received passkey.

Example 26 includes the subject matter of any of Examples 22-25, andwherein determining the personal profile identification comprisesauthenticating the user to the communal mobile communication device; andretrieving, in response to authentication of the user, a personalprofile identification from a personal profile database of the communalmobile communication device based on the authentication of the user.

Example 27 includes the subject matter of any of Examples 22-26, andwherein authenticating the user comprises determining whether a personalprofile identification for the authenticated user exists in the personalprofile database; and setting the personal profile identification to adefault personal profile identification in response to the personalprofile identification for the user not existing in the personal profiledatabase.

Example 28 includes the subject matter of any of Examples 22-27, andwherein determining the personal profile identification comprisesdetermining a numerical sequence that uniquely identifies the user fromother authorized users of the communal mobile communication device.

Example 29 includes the subject matter of any of Examples 22-28, andwherein determining the personal profile identification comprisesretrieving an e-mail address that uniquely identifies the user fromother authorized users of the communal mobile communication device.

Example 30 includes the subject matter of any of Examples 22-29, andwherein determining the personal profile identification comprisesretrieving a passkey that uniquely identifies the user from otherauthorized users of the communal mobile communication device.

Example 31 includes the subject matter of any of Examples 22-30, andwherein determining the phone number of the personal mobilecommunication device comprises retrieving the phone number from acontacts database.

Example 32 includes the subject matter of any of Examples 22-31, andwherein determining the phone number of the personal mobilecommunication device comprises receiving the phone number from the uservia a user interface.

Example 33 includes the subject matter of any of Examples 22-32, andwherein initiating the call comprises appending the phone number of thecommunal mobile communication device to the phone number of the personalmobile communication device.

Example 34 includes the subject matter of any of Examples 22-33, andwherein initiating the call comprises appending the personal profileidentification to the phone number of the communal mobile communicationdevice and the phone number of the personal mobile communication device.

Example 35 includes the subject matter of any of Examples 22-34, andwherein initiating the call comprises generating an outgoing phonenumber comprising (i) the phone number of the personal mobilecommunication device, (ii) the phone number of the communal mobilecommunication device, and (iii) the personal profile identification.

Example 36 includes the subject matter of any of Examples 22-35, andfurther including recording call metrics of the call for the user of thecommunal mobile communication device.

Example 37 includes the subject matter of any of Examples 22-36, andfurther including receiving an incoming call on the communal mobilecommunication device, the incoming call including a personal profileidentification identifying a call recipient to receive the call; anddetermining a call treatment for the incoming call based on the personalprofile identification; and announcing the incoming call on the communalmobile communication device using the determined call treatment.

Example 38 includes the subject matter of any of Examples 22-37, andwherein determining the call treatment for the incoming call comprisesretrieving call treatment data from an incoming call policy databasebased on the personal profile identification.

Example 39 includes the subject matter of any of Examples 22-38, andwherein determining a call treatment comprises applying a default calltreatment in response to the personal profile identification notexisting in an incoming call policy database of the communal mobilecommunication device.

Example 40 includes the subject matter of any of Examples 22-39, andwherein determining the call treatment comprises retrieving an imageassociated with the call recipient based on the personal profileidentification, and announcing the incoming call comprises displayingthe image on a display of the communal mobile communication device.

Example 41 includes the subject matter of any of Examples 22-40, andwherein determining the call treatment comprises retrieving a ringtoneassociated with the call recipient based on the personal profileidentification, and announcing the incoming call comprises playing theringtone on the communal mobile communication device.

Example 42 includes the subject matter of any of Examples 22-41, andwherein announcing the incoming call comprises displaying identificationdata of a caller based on a phone number of a personal communicationdevice that originated the incoming call.

Example 43 includes one or more machine readable storage mediacomprising a plurality of instructions stored thereon that in responseto being executed result in a computing device performing the method ofany of Examples 22-42.

Example 44 includes a communal mobile communication device for handlingcalls based on user identification, the communal mobile communicationdevice comprising means for determining a personal profileidentification for a user of a communal mobile communication device, thepersonal profile identification identifying the user from other users ofthe communal mobile communication device; means for determining, on thecommunal mobile communication device, a phone number of a personalmobile communication device of a call recipient selected to receive thecall; and means for initiating the call from the communal mobilecommunication device to the personal mobile communication device usingthe phone number and the personal profile identification to identify theuser.

Example 45 includes the subject matter of Example 44, and wherein themeans for determining the personal profile identification comprisesmeans for presenting a menu of authorized users of the communal mobilecommunication device on a display of the communal mobile communicationdevice; means for receiving a selection of one of the authorized users;and means for retrieving a personal profile identification of theselected authorized user from a personal profile database.

Example 46 includes the subject matter of any of Examples 44 and 45, andwherein the means for retrieving a personal profile identificationcomprising means for authenticating the user to access the personalprofile identification; and means for retrieving the personal profileidentification from a personal profile database of the communal mobilecommunication device in response to authenticating the user.

Example 47 includes the subject matter of any of Examples 44-46, andwherein the means for authenticating the user comprises means forreceiving a passkey from the user via a user interface of the communalmobile communication device and authenticating the user based on thereceived passkey.

Example 48 includes the subject matter of any of Examples 44-47, andwherein the means for determining the personal profile identificationcomprises means for authenticating the user to the communal mobilecommunication device; and means for retrieving, in response toauthentication of the user, a personal profile identification from apersonal profile database of the communal mobile communication devicebased on the authentication of the user.

Example 49 includes the subject matter of any of Examples 44-48, andwherein the means for authenticating the user comprises means fordetermining whether a personal profile identification for theauthenticated user exists in the personal profile database; and meansfor setting the personal profile identification to a default personalprofile identification in response to the personal profileidentification for the user not existing in the personal profiledatabase.

Example 50 includes the subject matter of any of Examples 44-49, andwherein the personal profile identification comprises a numericalsequence that uniquely identifies the user from other authorized usersof the communal mobile communication device.

Example 51 includes the subject matter of any of Examples 44-50, andwherein the personal profile identification comprises an e-mail addressthat uniquely identifies the user from other authorized users of thecommunal mobile communication device.

Example 52 includes the subject matter of any of Examples 44-51 andwherein the personal profile identification comprises a passkey thatuniquely identifies the user from other authorized users of the communalmobile communication device.

Example 53 includes the subject matter of any of Examples 44-52, andwherein the means for determining the phone number of the personalmobile communication device comprises means for retrieving the phonenumber from a contacts database.

Example 54 includes the subject matter of any of Examples 44-53, andwherein the means for determining the phone number of the personalmobile communication device comprises means for receiving the phonenumber from the user via a user interface.

Example 55 includes the subject matter of any of Examples 44-54, andwherein the means for initiating the call comprises means for appendingthe phone number of the communal mobile communication device to thephone number of the personal mobile communication device.

Example 56 includes the subject matter of any of Examples 44-55, andwherein the means for initiating the call comprises means for appendingthe personal profile identification to the phone number of the communalmobile communication device and the phone number of the personal mobilecommunication device.

Example 57 includes the subject matter of any of Examples 44-56, andwherein the means for initiating the call comprises means for generatingan outgoing phone number comprising (i) the phone number of the personalmobile communication device, (ii) the phone number of the communalmobile communication device, and (iii) the personal profileidentification.

Example 58 includes the subject matter of any of Examples 44-57, andfurther including means for recording call metrics of the call for theuser of the communal mobile communication device.

Example 59 includes the subject matter of any of Examples 44-58, andfurther including means for receiving an incoming call on the communalmobile communication device, the incoming call including a personalprofile identification identifying a call recipient to receive the call;and means for determining a call treatment for the incoming call basedon the personal profile identification; and means for announcing theincoming call on the communal mobile communication device using thedetermined call treatment.

Example 60 includes the subject matter of any of Examples 44-59, andwherein the means for determining the call treatment for the incomingcall comprises means for retrieving call treatment data from a personalprofile database based on the personal profile identification.

Example 61 includes the subject matter of any of Examples 44-60, andwherein the means for determining a call treatment comprises means forapplying a default call treatment in response to the personal profileidentification not existing in a personal profile database of thecommunal mobile communication device.

Example 62 includes the subject matter of any of Examples 44-61, andwherein the means for determining the call treatment comprises means forretrieving an image associated with the call recipient based on thepersonal profile identification, and the means for announcing theincoming call comprises means for displaying the image on a display ofthe communal mobile communication device.

Example 63 includes the subject matter of any of Examples 44-62, andwherein the means for determining the call treatment comprises means forretrieving a ringtone associated with the call recipient based on thepersonal profile identification, and the means for announcing theincoming call comprises means for playing the ringtone on the communalmobile communication device.

Example 64 includes the subject matter of any of Examples 44-63, andwherein the means for announcing the incoming call comprises means fordisplaying identification data of a caller based on a phone number of apersonal communication device that originated the incoming call.

Example 65 includes a personal mobile communication device for handlinga call based on user identification, the personal mobile communicationdevice comprising a personal profile database having stored thereinpersonal profile identifications that identify users of a communalmobile communication device; and an outgoing call handler module to (i)determine a call recipient of a communal mobile communication device toreceive a call from a user of the personal mobile communication device,(ii) retrieve personal profile identification for the determined callrecipient from the personal profile database and (ii) initiate the callto the communal mobile communication device using a phone number of thecommunal mobile communication device and the personal profileidentification to identify the call recipient.

Example 66 includes the subject matter of Example 65, and wherein thepersonal profile identification comprises a numerical sequence thatuniquely identifies the call recipient from other authorized users ofthe communal mobile communication device.

Example 67 includes the subject matter of any of Examples 65 and 66, andwherein the personal profile identification comprises an e-mail addressthat uniquely identifies the call recipient from other authorized usersof the communal mobile communication device.

Example 68 includes the subject matter of any of Examples 65-67, andwherein the personal profile identification comprises a passkey thatuniquely identifies the call recipient from other authorized users ofthe communal mobile communication device.

Example 69 includes the subject matter of any of Examples 65-68, andwherein to initiate the call comprises to append the phone number of thepersonal mobile communication device to the phone number of the communalmobile communication device.

Example 70 includes the subject matter of any of Examples 65-69, andwherein to initiate the call comprises to append the personal profileidentification to the phone number of the personal mobile communicationdevice and the phone number of the communal mobile communication device.

Example 71 includes the subject matter of any of Examples 65-70, andwherein to initiate the call comprises generate an outgoing phone numbercomprising (i) the phone number of the communal mobile communicationdevice, (ii) the phone number of the personal mobile communicationdevice, and (iii) the personal profile identification.

Example 72 includes the subject matter of any of Examples 65-71, andfurther including an incoming call handler module to receive an incomingcall including a personal profile identification identifying a callerthat initiated the incoming call determine a call treatment for theincoming call based on the personal profile identification; and announcethe incoming call on the personal mobile communication device using thedetermined call treatment.

Example 73 includes the subject matter of any of Examples 65-72, andfurther including an incoming call policy database, and wherein todetermine the call treatment for the incoming call comprises to retrievecall treatment data from the incoming call policy database based on thepersonal profile identification.

Example 74 includes the subject matter of any of Examples 65-73, andfurther including an incoming call policy database, and wherein todetermine a call treatment comprises to apply a default call treatmentin response to the personal profile identification not existing in theincoming call policy database.

Example 75 includes the subject matter of any of Examples 65-74, andfurther including a display, and wherein to determine the call treatmentcomprises to retrieve an image associated with the caller based on thepersonal profile identification, and to announce the incoming callcomprises to display the image on the display.

Example 76 includes the subject matter of any of Examples 65-75, andwherein to determine the call treatment comprises retrieving a ringtoneassociated with the caller based on the personal profile identification,and to announce the incoming call comprises to play the ringtone on thepersonal mobile communication device.

Example 77 includes a method for handling a call based on useridentification, the method comprising determining, on a personal mobilecommunication device, a call recipient of a communal mobilecommunication device to receive a call from a user of the personalmobile communication device; retrieving personal profile identificationfor the determined call recipient from a personal profile database ofthe personal mobile communication device, the personal profileidentification identifying the call recipient from other users of thecommunal mobile communication device; and initiating the call from thepersonal mobile communication device to the communal mobilecommunication device using a phone number of the communal mobilecommunication device and the personal profile identification to identifythe call recipient.

Example 78 includes the subject matter of Example 77, and whereinretrieving the personal profile identification comprises retrieving anumerical sequence from the personal profile database that uniquelyidentifies the call recipient from other authorized users of thecommunal mobile communication device.

Example 79 includes the subject matter of any of Examples 77 and 78, andwherein retrieving the personal profile identification comprisesretrieving an e-mail address from the personal profile database thatuniquely identifies the call recipient from other authorized users ofthe communal mobile communication device.

Example 80 includes the subject matter of any of Examples 77-79, andwherein retrieving the personal profile identification comprisesretrieving a passkey from the personal profile database that uniquelyidentifies the call recipient from other authorized users of thecommunal mobile communication device.

Example 81 includes the subject matter of any of Examples 77-80, andwherein initiating the call comprises appending the phone number of thepersonal mobile communication device to the phone number of the communalmobile communication device.

Example 82 includes the subject matter of any of Examples 77-81, andwherein initiating the call comprises appending the personal profileidentification to the phone number of the personal mobile communicationdevice and the phone number of the communal mobile communication device.

Example 83 includes the subject matter of any of Examples 77-82, andwherein initiating the call comprises generating an outgoing phonenumber comprising (i) the phone number of the communal mobilecommunication device, (ii) the phone number of the personal mobilecommunication device, and (iii) the personal profile identification.

Example 84 includes the subject matter of any of Examples 77-83, andfurther including receiving an incoming call on the personal mobilecommunication device, the incoming call including a personal profileidentification identifying a caller that initiated the incoming calldetermining a call treatment for the incoming call based on the personalprofile identification; and announcing the incoming call on the personalmobile communication device using the determined call treatment.

Example 85 includes the subject matter of any of Examples 77-84, andwherein determining the call treatment for the incoming call comprisesretrieving call treatment data from an incoming call policy databasebased on the personal profile identification.

Example 86 includes the subject matter of any of Examples 77-85, andwherein determining a call treatment comprises applying a default calltreatment in response to the personal profile identification notexisting in an incoming call policy database of the personal mobilecommunication device.

Example 87 includes the subject matter of any of Examples 77-86, andwherein determining the call treatment comprises retrieving an imageassociated with the caller based on the personal profile identification,and announcing the incoming call comprises displaying the image on adisplay of the personal mobile communication device.

Example 88 includes the subject matter of any of Examples 77-87, andwherein determining the call treatment comprises retrieving a ringtoneassociated with the caller based on the personal profile identification,and announcing the incoming call comprises playing the ringtone on thepersonal mobile communication device.

Example 89 includes one or more machine readable storage mediacomprising a plurality of instructions stored thereon that in responseto being executed result in a computing device performing the method ofany of Examples 77-88.

Example 90 includes a personal mobile communication device for handlinga call based on user identification, the personal mobile communicationdevice comprising means for determining a call recipient of a communalmobile communication device to receive a call from a user of thepersonal mobile communication device; means for retrieving personalprofile identification for the determined call recipient from a personalprofile database of the personal mobile communication device, thepersonal profile identification identifying the call recipient fromother users of the communal mobile communication device; and means forinitiating the call from the personal mobile communication device to thecommunal mobile communication device using a phone number of thecommunal mobile communication device and the personal profileidentification to identify the call recipient.

Example 91 includes the subject matter of Example 90, and wherein thepersonal profile identification comprises a numerical sequence thatuniquely identifies the call recipient from other authorized users ofthe communal mobile communication device.

Example 92 includes the subject matter of any of Example 90 and 91, andwherein the personal profile identification comprises an e-mail addressthat uniquely identifies the call recipient from other authorized usersof the communal mobile communication device.

Example 93 includes the subject matter of any of Example 90-92, andwherein the personal profile identification comprises a passkey thatuniquely identifies the call recipient from other authorized users ofthe communal mobile communication device.

Example 94 includes the subject matter of any of Example 90-93, andwherein the means for initiating the call comprises means for appendingthe phone number of the personal mobile communication device to thephone number of the communal mobile communication device.

Example 95 includes the subject matter of any of Example 90-94, andwherein the means for initiating the call comprises means for appendingthe personal profile identification to the phone number of the personalmobile communication device and the phone number of the communal mobilecommunication device.

Example 96 includes the subject matter of any of Example 90-95, andwherein the means for initiating the call comprises means for generatingan outgoing phone number comprising (i) the phone number of the communalmobile communication device, (ii) the phone number of the personalmobile communication device, and (iii) the personal profileidentification.

Example 97 includes the subject matter of any of Example 90-96, andfurther including means for receiving an incoming call on the personalmobile communication device, the incoming call including a personalprofile identification identifying a caller that initiated the incomingcall means for determining a call treatment for the incoming call basedon the personal profile identification; and means for announcing theincoming call on the personal mobile communication device using thedetermined call treatment.

Example 98 includes the subject matter of any of Example 90-97, andwherein the means for determining the call treatment for the incomingcall comprises means for retrieving call treatment data from an incomingcall policy database based on the personal profile identification.

Example 99 includes the subject matter of any of Example 90-98, andwherein the means for determining a call treatment comprises means forapplying a default call treatment in response to the personal profileidentification not existing in an incoming call policy database of thepersonal mobile communication device.

Example 100 includes the subject matter of any of Example 90-99, andwherein the means for determining the call treatment comprises means forretrieving an image associated with the caller based on the personalprofile identification, and the means for announcing the incoming callcomprises means for displaying the image on a display of the personalmobile communication device.

Example 101 includes the subject matter of any of Example 90-100, andwherein the means for determining the call treatment comprises means forretrieving a ringtone associated with the caller based on the personalprofile identification, and the means for announcing the incoming callcomprises means for playing the ringtone on the personal mobilecommunication device.

1. A communal mobile communication device for handling calls based onuser identification, the communal mobile communication devicecomprising: an outgoing call handler module to (i) determine a personalprofile identification that identifies a user of the communal mobilecommunication device from other users, (i) determine a phone number of apersonal mobile communication device of a call recipient selected toreceive a call from the communal mobile communication device, and (iii)initiate the call to the personal mobile communication device using thephone number and the personal profile identification to identify theuser.
 2. The communal mobile communication device of claim 1, whereinthe communal mobile communication device further comprises a personalprofile database having stored therein personal profile identificationsfor users of the communal mobile communication device, and wherein todetermine the personal profile identification comprises to: authenticatethe user to the communal mobile communication device; and retrieve, inresponse to authentication of the user, a personal profileidentification from the personal profile database based on theauthentication of the user.
 3. The communal mobile communication deviceof claim 2, wherein to authenticate the user comprises to: determinewhether a personal profile identification for the authenticated userexists in the personal profile database; and set the personal profileidentification to a default personal profile identification in responseto the determination that the personal profile identification for theuser does not exist in the personal profile database.
 4. The communalmobile communication device of claim 1, wherein the personal profileidentification comprises at least one of (i) a numerical sequence thatuniquely identifies the user from other authorized users of the communalmobile communication device, (ii) an e-mail address that uniquelyidentifies the user from other authorized users of the communal mobilecommunication device, or (iii) a passkey that uniquely identifies theuser from other authorized users of the communal mobile communicationdevice.
 5. The communal mobile communication device of claim 1, whereinto initiate the call comprises to generate an outgoing phone numbercomprising (i) the phone number of the personal mobile communicationdevice, (ii) the phone number of the communal mobile communicationdevice, and (iii) the personal profile identification.
 6. The communalmobile communication device of claim 1, wherein the outgoing callhandler further to record call metrics of the call for the user of thecommunal mobile communication device.
 7. The communal mobilecommunication device of claim 1, further comprising an incoming callhandler module to: receive an incoming call including a personal profileidentification identifying a call recipient to receive the call;determine a call treatment for the incoming call based on the personalprofile identification; and announce the incoming call on the communalmobile communication device using the determined call treatment.
 8. Thecommunal mobile communication device of claim 7, further comprising apersonal profile database having stored therein personal profileidentifications for user of the communal mobile communication device,and wherein to determine the call treatment for the incoming callcomprises to retrieve call treatment data from the personal profiledatabase based on the personal profile identification.
 9. The communalmobile communication device of claim 7, wherein: to determine the calltreatment comprises to retrieve a ringtone associated with the callrecipient based on the personal profile identification, and to announcethe incoming call comprises to play the ringtone on the communal mobilecommunication device.
 10. One or more machine readable storage mediacomprising a plurality of instructions stored thereon that, in responseto being executed, causes a mobile communication device to: determine apersonal profile identification for a user of a communal mobilecommunication device, the personal profile identification identifyingthe user from other users of the communal mobile communication device;determine a phone number of a personal mobile communication device of acall recipient selected to receive the call; and initiate the call fromthe communal mobile communication device to the personal mobilecommunication device using the phone number and the personal profileidentification to identify the user.
 11. The machine readable storagemedia of claim 10, wherein to determine the personal profileidentification comprises to: authenticate the user to the communalmobile communication device; and retrieve, in response to authenticationof the user, a personal profile identification from a personal profiledatabase of the communal mobile communication device based on theauthentication of the user.
 12. The machine readable storage media ofclaim 11, wherein to authenticate the user comprises to: determinewhether a personal profile identification for the authenticated userexists in the personal profile database; and set the personal profileidentification to a default personal profile identification in responseto the personal profile identification for the user not existing in thepersonal profile database.
 13. The machine readable storage media ofclaim 10, wherein the personal profile identification comprises at leastone of: (i) a numerical sequence that uniquely identifies the user fromother authorized users of the communal mobile communication device, (ii)an e-mail address that uniquely identifies the user from otherauthorized users of the communal mobile communication device, or (iii) apasskey that uniquely identifies the user from other authorized users ofthe communal mobile communication device.
 14. The machine readablestorage media of claim 10, wherein to initiate the call comprises togenerate an outgoing phone number comprising (i) the phone number of thepersonal mobile communication device, (ii) the phone number of thecommunal mobile communication device, and (iii) the personal profileidentification.
 15. The machine readable storage media of claim 10,wherein the plurality of instructions, in response to being executed,further cause the mobile communication device to record call metrics ofthe call for the user of the communal mobile communication device. 16.The machine readable storage media of claim 10, wherein the plurality ofinstructions, in response to being executed, further cause the mobilecommunication device to: receive an incoming call on the communal mobilecommunication device, the incoming call including a personal profileidentification identifying a call recipient to receive the call;determine a call treatment for the incoming call based on the personalprofile identification; and announce the incoming call on the communalmobile communication device using the determined call treatment.
 17. Themachine readable storage media of claim 16, wherein to determine a calltreatment comprises to apply a default call treatment in response to thepersonal profile identification not existing in an incoming call policydatabase of the communal mobile communication device.
 18. A method forhandling a call based on user identification, the method comprising:determining a personal profile identification for a user of a communalmobile communication device, the personal profile identificationidentifying the user from other users of the communal mobilecommunication device; determining, on the communal mobile communicationdevice, a phone number of a personal mobile communication device of acall recipient selected to receive the call; and initiating the callfrom the communal mobile communication device to the personal mobilecommunication device using the phone number and the personal profileidentification to identify the user.
 19. The method of claim 18, whereindetermining the personal profile identification comprises:authenticating the user to the communal mobile communication device; andretrieving, in response to authentication of the user, a personalprofile identification from a personal profile database of the communalmobile communication device based on the authentication of the user. 20.The method of claim 19, wherein authenticating the user comprises:determining whether a personal profile identification for theauthenticated user exists in the personal profile database; and settingthe personal profile identification to a default personal profileidentification in response to the personal profile identification forthe user not existing in the personal profile database.